home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19990725-20000114
/
000042_news@columbia.edu _Thu Aug 19 15:48:23 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id PAA01626
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 19 Aug 1999 15:48:22 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id PAA23050
for kermit.misc@watsun.cc.columbia.edu; Thu, 19 Aug 1999 15:39:15 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: "Michael Hamelin" <hamelin@ici.net>
Subject: beta 6 Problem w/batch queue & USR-->USR Modem issue
Date: Thu, 19 Aug 1999 15:33:22 -0400
Organization: The Internet Connection
Message-ID: <7phlm8$nj0$1@bashir.ici.net>
To: kermit.misc@columbia.edu
1.) submiting a batch job into the vms queue, the displayed file
information..text version of the file transfer doesn't work. get can't open
tt: device
------
Beta 8 gives us...
%ckermit-w-notterm tt: is not a terminal
sorry can't open connecion tt:: error 0
???
Downloaded beta 9 for vms-55 (nonet) and got an error on image activivation
???
we are running batch jobs from fully priv account...not any issue under
version 5. 5 runs excellant as detailed...this failed in beta 195..not sure
if corrected yet. What we are saying here is that the computer spits out
TT: not an output device, where as version 5 works fine and you get to see
the file being transfered (serial transfer display). This is not the case
in BETA 195. NO DISPLAY is possible running from the batch queue. The same
username, script and command procedure run from version 5 and beta 195,
this is the issue we are now facing. Only change is the ckermit
version....Saw a not about this is the release notes, not sure what it
meant. Just giving you pre-post results..
2.) USR to USR still will not make a connect in ckermit. Ckermit is still
getting the data and starting the login process, instead of just making the
connect. We have solved it temp. by using a zoom modem as the dialer and
the usr sportsters 33.6k modems in the field (34 stores). ckermit makes a
connect and then the scripts appear to be fine after that.
(frank's comments)
>I don't understand the complaint. What, precisely, do you mean by
>"connect"?
>You say "Ckermit is still getting the data and starting the login process,
instead of just making the connect." You don't want it to get the data and
start the login process? I can't help but suspect that it is only doing
what
your script is telling it to do...
(us)
we sent you the scripts before...will send again if needed...we found a bug
in the handshaking of the login scripts for vmslogin. new stuff was added,
but the computer appears not to like it, so we used the logic from version
5 and it corrected the problem on login. The issue is still the same with
USR to USR. If we use the USR in the stores and the ZOOM , HAYES, Anything
but USR, CKERMIT does it thing correctly.
The USR Will connect ..handshake and start the login process on the vax
(waking the port up), the zoom and others only handshake and wait. The
modem settings on the USR are identical to the ZOOM and IDentical to the
remote modem. A Manual dial with USR to USR, will never get a connect
message...you will see data on the screen and the VMSLOGIN is confused and
the call complete never occurs. If you substitute the ZOOM for the USR as
the dialer, all is fine. We DONT CARE ANYMORE....but, Thought you might
want to know..since this is in BETA. We have bought ZOOMS as the dialers to
get away from the problem, BUT IT IS STILL A PROBLEM for others i am sure.
Dialer is ALPHA VMS 6.2-H3, receiver is VAX VMS 5.5-2...fyi...
any thoughts, comments.....